home *** CD-ROM | disk | FTP | other *** search
-
-
-
- ccccrrrroooonnnn((((1111MMMM)))) ccccrrrroooonnnn((((1111MMMM))))
-
-
-
- NNNNAAAAMMMMEEEE
- cron - clock daemon
-
- SSSSYYYYNNNNOOOOPPPPSSSSIIIISSSS
- ccccrrrroooonnnn [ ----jjjj _j_o_b_s ] [ nnnnooooffffoooorrrrkkkk ]
-
- DDDDEEEESSSSCCCCRRRRIIIIPPPPTTTTIIIIOOOONNNN
- _c_r_o_n executes commands at specified dates and times. Regularly scheduled
- commands can be specified according to instructions found in _c_r_o_n_t_a_b
- files in the directory /_v_a_r/_s_p_o_o_l/_c_r_o_n/_c_r_o_n_t_a_b_s. Users can submit their
- own _c_r_o_n_t_a_b file via the _c_r_o_n_t_a_b(1) command. Commands that are to be
- executed only once can be submitted using the _a_t(1) command.
-
- The following options are supported:
-
- ----jjjj _j_o_b_s Specify the maximum number of jobs (MAXRUN) that _c_r_o_n can
- simultaneously run. The default value is 25. The maximum
- allowed value is 250.
-
- nnnnooooffffoooorrrrkkkk If this option is supplied, _c_r_o_n runs in the foreground.
-
- _c_r_o_n examines _c_r_o_n_t_a_b files and _a_t command files only during process
- initialization and when a file changes via _c_r_o_n_t_a_b or _a_t. This reduces
- the overhead of checking for new or changed files at regularly scheduled
- intervals.
-
- Since _c_r_o_n never exits, it should be executed only once. This is done
- routinely through /_e_t_c/_r_c_2._d/_S_7_5_c_r_o_n at system boot time.
- /_e_t_c/_c_r_o_n._d/_F_I_F_O is used as a lock file to prevent the execution of more
- than one _c_r_o_n and is also used by the _c_r_o_n_t_a_b command for notification of
- changes to the _c_r_o_n_t_a_b files.
-
- If MAXRUN jobs are running and another is scheduled, _c_r_o_n does not run
- the new job. A message is logged via _s_y_s_l_o_g(3C).
-
- _c_r_o_n attempts to handle changes to the system date correctly, either
- forward or backward. There may be some delay for jobs scheduled during
- the interval on large forward-time changes.
-
- For each job launched, cron reads in configuration information from
- /_e_t_c/_d_e_f_a_u_l_t/_c_r_o_n. Currently the only option supported is the
- SVR4_SIGNALS option, which may be set to `YES' or `NO' (it defaults to
- NO). Setting SVR4_SIGNALS to `YES' will result in processes forked with
- the SIGXFSZ and SIGXCPU signals ignored. For CPU and filesize resource
- limiting to work correctly, SVR4_SIGNALS should be set to `NO', so that
- these signal retain their default behaviour, which is to terminate the
- process.
-
- If the file ////eeeettttcccc////ccccrrrroooonnnn....dddd////ccccrrrroooonnnn....aaaalllllllloooowwww exists, only users whose names appear
- in the file are permitted to use _c_r_o_n_t_a_b. This restriction applies to all
- users, including root. If that file does not exist, the file
- ////eeeettttcccc////ccccrrrroooonnnn....dddd////ccccrrrroooonnnn....ddddeeeennnnyyyy is checked to determine if the user should be
-
-
-
- PPPPaaaaggggeeee 1111
-
-
-
-
-
-
- ccccrrrroooonnnn((((1111MMMM)))) ccccrrrroooonnnn((((1111MMMM))))
-
-
-
- denied access to _c_r_o_n_t_a_b. If neither file exists, only root is allowed to
- submit a job. If ccccrrrroooonnnn....aaaalllllllloooowwww does not exist and ccccrrrroooonnnn....ddddeeeennnnyyyy exists but is
- empty, global usage is permitted. The allow/deny files consist of one
- user name per line.
-
- FFFFIIIILLLLEEEESSSS
- /etc/cron.d main cron directory
- /etc/cron.d/FIFO used as a lock file against multiple copies
- running and also for notification of new or
- changed _c_r_o_n_t_a_b files
- /etc/cron.d/cron.allow only users whose names appear in the file are
- permitted to use _c_r_o_n_t_a_b.
- /etc/cron.d/cron.deny only users whose names appear in the file are
- denied access to _c_r_o_n_t_a_b.
- /var/cron/log accounting information
- /var/spool/cron spool area
- /etc/config/cron.options site-dependent options /etc/default/cron
- default behaviour configuration file
-
- SSSSIIIIGGGGNNNNAAAALLLLSSSS
- A SIGHUP signal can be sent to _c_r_o_n to cause it to reexamine all the
- _c_r_o_n_t_a_b and configuration files. A message is logged for this event.
- The SIGTERM signal should be used to shut _c_r_o_n down cleanly.
-
- SSSSEEEEEEEE AAAALLLLSSSSOOOO
- at(1), crontab(1), sh(1).
-
- DDDDIIIIAAAAGGGGNNNNOOOOSSSSTTTTIIIICCCCSSSS
- A history of all actions taken by _c_r_o_n is recorded in /_v_a_r/_c_r_o_n/_l_o_g.
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
- PPPPaaaaggggeeee 2222
-
-
-
-